feat(agents): carry the provisioning content digest algorithm on the wire - #509
Conversation
…wire A bare string digest pins the algorithm in a comment and cannot evolve; a Digest value object keeps the contract honest about what committed the bytes and clarifies the placement semantics of parent. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
PR SummaryMedium Risk Overview
Reusing field 6 with a new wire type is intentionally breaking for any prior encodings of this unreleased event; callers must populate and verify Reviewed by Cursor Bugbot for commit 1996b64. Bugbot is set up for automated code reviews on this repo. Configure here. |
WalkthroughThe protobuf contract introduces a required ChangesAgent digest schema
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Code Coverage SummaryDetailsDiff against mainResults for commit: 1996b64 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
stringdigest pins the hash algorithm in a comment, so it cannot evolve and forces every consumer to assume SHA-256 by convention; aDigestvalue object keeps the contract self-describing and consistent with how every other digest in the codebase is modeled.parentfield's placement semantics and immutability were implicit; documenting them prevents consumers from mistaking it for a mutable or kinship reference.